Artifact: Measurement Plan
|
|
Define the measurement goals, the associated metrics, and the primitive metrics to be collected in the project to monitor its progress. |
| Worker: | Project Manager |
| Template: | |
| Guidelines: | Guidelines: Metrics |
|
|
| Input to Activities: | Output from Activities: |
Purpose
The software measurement plan specifies which primitive metrics should be collected and which metrics should be computed during the project to monitor progress, relative to a set of specified project goals (see Concepts: Metrics). It is used to collect information on the project as input to the periodic Status Assessment (see Artifact: Status Assessment).
Brief
Outline
(hyperlinks into HTML template in a new window)
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 References
1.5 Overview
2. Management Goals and Subgoals
3. Metrics
3.1 Template for a metric:
4. Primitive Metrics
4.1 Template for a Primitive Metric:
5. Annexes
Timing
The measurement plan is done once per development cycle, in the inception phase, as part of the general planning activity, or sometimes as part of the configuration of the process in the development case. The measurement plan may be revisited like any other section of the software development plan during the course of the project.
Responsibility
The Worker: Project Manager is responsible for the integrity of the measurement plan, ensuring that:
- the goals are relevant to the project.
- the primitive metrics can all be collected at minimal overhead, and if possible using tools.
The Measurement Plan is a part of the more general Artifact: Software Development Plan.
Tailoring
The Measurement Plan may be physically part of the Software Development Plan if the metrics program is a simple one.
